Ventilation system

ABSTRACT

A ventilator system includes a ventilation device, and is configured to operate in a passive mode configured to transmit ventilation data in response to requests from a ventilation management system, or an active mode configured to automatically transmit ventilation data as the data becomes available. The system receives ventilation system data associated with operation of the ventilation device, modifies one or more operating parameters of the ventilation device based on the received ventilation system data, receives ventilator data associated with the ventilator device, determines an alarm associated with the ventilator device or a patient based on the received ventilator data and, responsive to determining the alarm, sends the alarm to a beginning of a transmission queue for transmitting the ventilation data to the ventilation management system, wherein the alarm is communicated over the network prior to other ventilation data in the transmission queue.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 16/854,785, entitled “VENTILATION SYSTEM,” filed on Apr. 21, 2020,which is a continuation application of U.S. application Ser. No.15/654,414, entitled “VENTILATION SYSTEM,” filed on Jul. 19, 2017, nowU.S. Pat. No. 10,646,673, which is a continuation of U.S. applicationSer. No. 13/830,830, entitled “VENTILATION SYSTEM,” filed on Mar. 14,2013, now U.S. Pat. No. 9,737,676 which is a continuation-in-part ofU.S. application Ser. No. 13/287,419, entitled “BI-DIRECTIONALVENTILATOR COMMUNICATION,” filed on Nov. 2, 2011, the entirety of eachof which is incorporated herein by reference.

BACKGROUND Field

The present disclosure generally relates to medical devices, and moreparticularly to the configuration of a ventilator.

Description of the Related Art

Medical ventilation systems (or “ventilators,” colloquially called“respirators”) are machines that are typically used to mechanicallyprovide breathable air or blended gas to lungs in order to assist apatient in breathing. Ventilation systems are chiefly used in intensivecare medicine, home care, emergency medicine, and anesthesia. Commonventilation systems are limited to a single direction of communication,and as such are configured to provide information related to theventilation system for display, but not receive information from aremote source for any purpose to control the ventilator. For example,common ventilation systems send outbound data to another entity, such asa display device, in order to display ventilator settings.

SUMMARY

According to certain embodiments of the present disclosure, aventilation system is provided. The system includes a ventilation devicethat is configured to provide breathable air or gas mixture to a patientaccording to certain operating parameters, a memory that includesinstructions, and a processor. The processor is configured to executethe instructions to receive, over a network, at least one of patientdata, order data, configuration data, user data, or rules or protocols,and provide a modification of operating parameters of the ventilationdevice based on the received patient data, order data, configurationdata, user data, or rules or protocols.

According to certain embodiments of the present disclosure, a method forconfiguring a ventilator is provided. The method includes receiving,over a network, at least one of patient data, order data, configurationdata, user data, or rules or protocols, and providing a modification ofoperating parameters of a ventilation device that is configured toprovide breathable air or gas mixture to a patient according to theoperating parameters based on the received patient data, order data,configuration data, user data, or rules or protocols.

According to certain embodiments of the present disclosure, amachine-readable storage medium includes machine-readable instructionsfor causing a processor to execute a method for configuring a ventilatoris provided. The method includes receiving, over a network, at least oneof patient data, order data, configuration data, user data, or rules orprotocols, and providing a modification of operating parameters of aventilation device that is configured to provide breathable air or gasmixture to a patient according to the operating parameters based on thereceived patient data, order data, configuration data, user data, orrules or protocols.

According to certain embodiments of the present disclosure, a ventilatormanagement system is provided. The system includes a memory thatincludes an initial configuration profile configured to designateoperating parameters for a ventilation device, and a processor. Theprocessor is configured to receive ventilator data from the ventilationdevice, the ventilator data includes at least one of operatingparameters of the ventilation device or physiological statistics of apatient associated with the ventilation device, and determine, based onthe ventilator data, a modification to the initial configuration profilefor the ventilation device. The processor is also configured to generatea modified configuration profile for the ventilation device based on thedetermined modification.

According to certain embodiments of the present disclosure, a method formanaging a plurality of ventilators is provided. The method includesreceiving ventilator data from the ventilation device, the ventilatordata includes at least one of operating parameters of the ventilationdevice or physiological statistics of a patient associated with theventilation device, and determining, based on the ventilator data, amodification to an initial configuration profile for the ventilationdevice. The method also includes generating a modified configurationprofile for the ventilation device based on the determined modification.

According to certain embodiments of the present disclosure, amachine-readable storage medium includes machine-readable instructionsfor causing a processor to execute a method for managing a plurality ofventilators is provided. The method includes receiving ventilator datafrom the ventilation device, the ventilator data includes at least oneof operating parameters of the ventilation device or physiologicalstatistics of a patient associated with the ventilation device, anddetermining, based on the ventilator data, a modification to an initialconfiguration profile for the ventilation device. The method alsoincludes generating a modified configuration profile for the ventilationdevice based on the determined modification.

It is understood that other configurations of the subject technologywill become readily apparent to those skilled in the art from thefollowing detailed description, wherein various configurations of thesubject technology are shown and described by way of illustration. Aswill be realized, the subject technology is capable of other anddifferent configurations and its several details are capable ofmodification in various other respects, all without departing from thescope of the subject technology. Accordingly, the drawings and detaileddescription are to be regarded as illustrative in nature and not asrestrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide furtherunderstanding and are incorporated in and constitute a part of thisspecification, illustrate disclosed embodiments and together with thedescription serve to explain the principles of the disclosedembodiments. In the drawings:

FIG. 1 illustrates an example architecture for a ventilator managementsystem.

FIG. 2 is a block diagram illustrating an example ventilation system,ventilation management system, and home ventilation device from thearchitecture of FIG. 1 according to certain aspects of the disclosure.

FIG. 3 illustrates an example flow chart of exchanging data between aventilation system and a ventilation management system.

FIG. 4 illustrates an example flow chart for a communication protocolused by the ventilation system of FIG. 3.

FIG. 5 illustrates example processes for contextualizing ventilator datafor a ventilation system.

FIGS. 6A and 6B illustrate example flow charts for caching data on aventilation system and a ventilation management system.

FIG. 7 illustrates an example process for managing a ventilation system.

FIG. 8 is a block diagram illustrating an example computer system withwhich the example ventilation system, ventilation management system, andhome ventilation device of FIG. 2 can be implemented.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a full understanding of the present disclosure. It willbe apparent, however, to one ordinarily skilled in the art that theembodiments of the present disclosure may be practiced without some ofthese specific details. In other instances, well-known structures andtechniques have not been shown in detail so as not to obscure thedisclosure.

Certain aspects of the disclosed system provide ventilation systems withtwo-way communication. Specifically, in addition to permitting aventilation system to output basic ventilation data such asphysiological statistics, the disclosed ventilation systems permitoutput of additional information such as ventilator settings,notifications, patient information, ventilation waveforms, loops ortrended data (“scalars”), and ventilation monitoring information. Thedisclosed ventilation systems also permit input of configurationprofiles, rules and protocols, user data, notifications, preprogramming,patient data, and lab results. The disclosed ventilation systems areconfigured to operate according to the received configuration profiles,rules, and clinical protocols, and in view of the user data,notifications, preprogramming, patient data, and lab results. The datafor the ventilation system can also be “contextualized” (e.g.,associated with a patient and/or caregiver) using various wired andwireless techniques. The disclosed ventilation systems are configured toprovide the output of additional information to, for example, aventilation management system.

The disclosed ventilation management system is configured to receive theinformation from one or many ventilation systems, analyze theinformation, and determine new or modified configuration profiles,rules, and clinical protocols from the received information. Theinformation may be received wired or wirelessly over a network. Thedisclosed ventilation management system is also configured to providethe new or modified configuration profiles, rules, and clinicalprotocols back to one or many of the ventilation systems. Theventilation systems managed by the ventilation management system can belocated either in a healthcare institution (e.g., a hospital) or outsideof a healthcare institution (e.g., a home or other care site). Both theventilation systems and the ventilation management systems areconfigured to cache data, for example, when the network is notavailable, so that data may be saved for later transmission.

FIG. 1 illustrates an example architecture 10 for a ventilatormanagement system. The architecture 10 includes a ventilation system 102and a hospital ventilation management system 14 connected over a localarea network (LAN) 119 in a hospital 101, and a home ventilation device130 in a home 140 connected to a wide area ventilation management system16 over a wide area network (WAN) 120. The hospital ventilationmanagement system 14, which can be configured, for example, by aclinician 12, other healthcare provider, or administrator, is connectedto the wide area ventilation management system 16 through the WAN 120.Furthermore, the home ventilation device 130 may operate substantiallysimilar to, and be configured substantially the same as, the ventilationsystem 102 of the hospital 101, except that the home ventilation device130 operates in the home 140.

Each of the ventilation systems 102 is configured to mechanically movebreathable air or a gas mixture into and out of lungs in order to assista patient in breathing. The ventilation systems 102 can provideventilator data, such as notifications, settings, monitor information(e.g., physiological statistics), and scalars to the hospitalventilation management system 14. The ventilation system 102 includes adevice having appropriate processor, memory, and communicationscapabilities for processing and providing ventilator data to thehospital ventilation management system 14. Similarly, the hospitalventilation management system 14 is configured to provide user data,notifications, pre-programmed instructions, lab results, patient data,configuration information, and rules and clinical protocols to eachventilation system 102 in the hospital 101 in order to configure eachventilation system 102 (e.g., remotely over a wired or wireless network,such as LAN 119). The information provided by the hospital ventilationmanagement system 14 to each ventilation system 102 can be based on theinformation provided to the hospital ventilation management system 14 byeach ventilation system 102.

For example, a ventilation system 102 can provide the hospitalventilation management system 14 with a current configuration profileand current monitor information for a patient associated with theventilation system 102. The hospital ventilation management system 14can analyze the information provided by the ventilation system 102 inorder to determine which modifications, if any, to make to theconfiguration profile in view of the patient's monitor information. Thehospital ventilation management system 14 may then provide a modifiedconfiguration profile to the ventilation system 102 so that theventilation system 102 may treat the patient in accordance with themodified configuration profile.

The hospital ventilation management system 14 is connected to a widearea ventilation management system 16 configured to manage one or manyhome ventilation devices 130. Although the hospital ventilationmanagement system 14 and the wide area ventilation management system 16are illustrated as being separate systems, both the hospital ventilationmanagement system 14 and the wide area ventilation management system 16can be hosted or otherwise executed from a single server. In certainaspects, many servers may share the hosting responsibilities of thehospital ventilation management system 14 and the wide area ventilationmanagement system 16. The server can be any device having an appropriateprocessor, memory, and communications capability for hosting thehospital ventilation management system 14 and the wide area ventilationmanagement system 16, and can be in a hospital data center or remotelyhosted over a network.

The WAN 120 can include, for example, any one or more of a metropolitanarea network (MAN), a wide area network (WAN), a broadband network(BBN), the Internet, and the like. The LAN 119 can include, for example,a personal area network (PAN) or campus area network (CAN). Further,each of the WAN 120 and LAN 119 can include, but is not limited to, anyone or more of the following network topologies, including a busnetwork, a star network, a ring network, a mesh network, a star-busnetwork, tree or hierarchical network, and the like.

An example use of the ventilator management system will now be provided.A patient associated with the ventilation system 102 is discharged by aclinician 12 from the hospital 101 but still requires ventilation usinghome ventilation device 130 in the patient's home 140. The hospitalventilation management system 14 registers with the wide areaventilation management system 16, and then sends the patient'sinformation and ventilator information from the ventilation system 102for the patient to the wide area ventilation management system 16. Thehome ventilation device 130 is configured using the patient'sinformation and ventilator information and the patient begins treatmentusing the home ventilation device 130. The clinician monitors thepatient's progress with the home ventilation device 130 by reviewinglogs from the home ventilation device 130 that are sent to the hospitalventilation management system 14 through the wide area ventilationmanagement system 16. As needed, the clinician may modify theconfiguration parameters of the home ventilation device 130 remotely bysending new configuration parameters from the hospital ventilationmanagement system 14 to the wide area ventilation management system 16,which then sends the new configuration parameters to the homeventilation device 130 for review by the patient or caregiver. Thepatient or caregiver accepts the new configuration parameters and thehome ventilation device 130 begins to operate according to the newconfiguration parameters.

FIG. 2 is a block diagram illustrating an example ventilation system102, ventilation management system 150, and home ventilation device 130from the architecture 10 of FIG. 1 according to certain aspects of thedisclosure. Although the ventilation management system 150 isillustrated as connected to a ventilation system 102 and a homeventilation device 130, the ventilation management system 150 isconfigured to also connect to infusion pumps, point of care vital signsmonitors, and pulmonary diagnostics devices.

The ventilation system 102 is connected to the ventilation managementsystem 150 over the LAN 119 via respective communications modules 110and 160 of the ventilation system 102 and the ventilation managementsystem 150. The ventilation management system 150 is connected over WAN120 to the home ventilation device 130 via respective communicationsmodules 160 and 146 of the ventilation management system 150 and thehome ventilation device 130. The home ventilation device 130 isconfigured to operate substantially similar to the ventilation system102 of the hospital 101, except that the home ventilation device 130 isconfigured for use in the home 140. The communications modules 110, 160,and 146 are configured to interface with the networks to send andreceive information, such as data, requests, responses, and commands toother devices on the networks. The communications modules 110, 160, and146 can be, for example, modems or Ethernet cards.

The ventilation management system 150 includes a processor 154, thecommunications module 160, and a memory 152 that includes hospital data156 and a ventilation management application 158. Although oneventilation system 102 is shown in FIG. 2, the ventilation managementsystem 150 is configured to connect with and manage many ventilationsystems 102, both ventilation systems 102 for hospitals 101 and homeventilation devices 130 for use in the home 140.

In certain aspects, the ventilation management system 150 is configuredto manage many ventilation systems 102 in the hospital 101 according tocertain rules and procedures. For example, when powering on, aventilation system 102 may send a handshake message to the ventilationmanagement system 150 to establish a connection with the ventilationmanagement system 150. Similarly, when powering down, the ventilationsystem 102 may send a power down message to the ventilation managementsystem 150 so that the ventilation management system 150 ceasescommunication attempts with the ventilation system 102.

The ventilation management system 150 is configured to support aplurality of simultaneous connections to different ventilation systems102 and home ventilation devices 130. The number of simultaneousconnections can be configured by an administrator in order toaccommodate network communication limitations (e.g., limited bandwidthavailability). After the ventilation system 102 successfully handshakeswith (e.g., connects to) the ventilation management system 150, theventilation management system 150 may initiate communications to theventilation system 102 when information becomes available, or atestablished intervals. The established intervals can be configured by auser so as to ensure that the ventilation system 102 does not exceed anestablished interval for communicating with the ventilation managementsystem 150.

The ventilation management system 150 can provide the data to theventilation system 102 in a first-in-first-out (FIFO) order. Forinstance, if a software upgrade is scheduled to be sent to a ventilationsystem 102, the software upgrade can be deployed at configurabletimeframes in FIFO order for the specified ventilation systems 102. Uponreceipt, a ventilation system 102 may initialize the software upgrade ona manual reboot. An admit-discharge-transfer communication can be sentto specified ventilation systems 102 within a certain care area of thehospital 101. A configuration profile communication can be sent to allventilation systems 102 connected to the ventilation management system150. On the other hand, orders specific to a patient are sent to theventilation system 102 associated with the patient.

The ventilation system 102 may initiate a communication to theventilation management system 150 if an alarm occurs on the ventilationsystem 102. The alarm may be sent to the beginning of the queue forcommunicating data to the ventilation management system 150. All otherdata of the ventilation system 102 may be sent together at once, or asubset of the data can be sent at certain intervals.

The hospital data 156 includes configuration profiles configured todesignate operating parameters for the ventilation system 102, operatingparameters of the ventilation system 102 and/or physiological statisticsof a patient associated with the ventilation system 102. Hospital data156 also includes patient data for patients at the hospital 101, order(e.g., medication orders, respiratory therapy orders) data for patientsat the hospital 101, and/or user data (e.g., for caregivers associatedwith the hospital 101).

The physiological statistics of the ventilator data includes, forexample, a statistic for compliance of the lung (Cdyn, Cstat), flowresistance of the patient airways (Raw), inverse ratio ventilation (FE),spontaneous ventilation rate, exhaled tidal volume (Vte), total lungventilation per minute (Ve), peak expiratory flow rate (PEFR), peakinspiratory flow rate (PIFR), mean airway pressure, peak airwaypressure, an average end-tidal expired CO2 and total ventilation rate.The operating parameters include, for example, a ventilation mode, a setmandatory tidal volume, positive end respiratory pressure (PEEP), anapnea interval, a bias flow, a breathing circuit compressible volume, apatient airway type (for example endotracheal tube, tracheostomy tube,face mask) and size, a fraction of inspired oxygen (FiO2), a breathcycle threshold, and a breath trigger threshold.

The processor 154 of the ventilation management system 150 is configuredto execute instructions, such as instructions physically coded into theprocessor 154, instructions received from software (e.g., ventilationmanagement application 158) in memory 152, or a combination of both. Forexample, the processor 154 of the ventilation management system 150executes instructions to receive ventilator data from the ventilationsystem 102 (e.g., including an initial configuration profile for theventilation system 102).

FIG. 3 illustrates an example flow chart 300 of exchanging data betweenthe ventilation system 102 and the ventilation management system 150. Asillustrated in the flow chart 300, the ventilation system 102 isconfigured to send ventilator information, notifications (or “alarms”),scalars, operating parameters 106 (or “settings”), physiologicalstatistics (or “monitors”) of a patient associated with the ventilationsystem 102, and general information. The notifications includeoperational conditions of the ventilation system 102 that may requireoperator review and corrective action. The scalars include parametersthat are typically updated periodically (e.g., every 500 ms) and can berepresented graphically on a two-dimensional scale. The physiologicalstatistics represent information that the ventilation system 102 ismonitoring, and can dynamic based on a specific parameter. The operatingparameters 106 represent the operational control values that thecaregiver has accepted for the ventilation system 102. The generalinformation can be information that is unique to the ventilation system102, or that may relate to the patient (e.g., a patient identifier). Thegeneral information can include an identifier of the version and modelof the ventilation system 102.

In the example of FIG. 3, the data is sent via a serial connector. Thedata is sent to a wired adapter 304 having a serial connector and a TCPconnector 308. The data is sent using any appropriate communicationprotocol 400 (e.g., VOXP protocol). FIG. 4 illustrates an example flowchart for a communication protocol, the VOXP protocol, used by theventilation system 102 of FIG. 3.

The communication protocol 400 of FIG. 4 is configured, in certainaspects, to operate in an active mode and a passive mode. In activemode, the ventilation system 102 both responds to requests (e.g., fromthe ventilation management system 150), as well as automatically sendsdata as it becomes available to the ventilation system 102. In passivemode, the ventilation system 102 responds to requests but does notautomatically send data as it becomes available. The protocol 400 beginsby transition from a dormant (or “passive”) mode 401 to starting theVOXP protocol 402 (e.g., to enter into active mode). When thecommunication input/output port is ready, a connection is established403 with the destination (e.g., wired adapter 304). If the connection isestablished without a ventilation device 118 being connected to theventilation system 102, then the protocol instructs to wait for docking404 (e.g., of a ventilation device 118). If a connection is broken whilewaiting for docking, the link between the ventilation system 102 and thedestination is reestablished 405. Otherwise, when a ventilation device118 is docked, or a connection is established, the protocol waits for aprofile or other data request 406 (e.g., from the ventilation managementsystem 150). If the connection is broken while waiting for the profilerequest, the link between the ventilation system 102 and the destinationis reestablished. When the profile request is received, ventilationsystem 102 sends a configuration profile 108 (specifying thecapabilities of the ventilation system 102 and the set of operatingparameters and other data that it can provide), and then the protocolwaits for a configuration command 407 (e.g., from the ventilationmanagement system 150). When the configuration command is received, alink is established with the destination and the link is configured 408.If while configuring the link there is a processing error, a modechanges, or the link is restarted, the link is again reestablished 405.Otherwise, upon configuring the link 408, the protocol for theventilation system 102 may enter a passive mode 409 or active mode 410.In passive mode 409, the ventilation management system 150 sendsrequests, at intervals determined by the ventilation managementapplication 158, for specified information. At each such request, theventilation system 102 responds with the specified information 318,which may include notifications (or “alarms”), scalars, operatingparameters 106 (or “settings”), and physiological statistics (or“monitors”) of a patient associated with the ventilation system 102. Inactive mode 410, the ventilation system 102 sends specified information318, which may include notifications (or “alarms”), scalars, operatingparameters 106 (or “settings”), and physiological statistics (or“monitors”) of a patient associated with the ventilation system 102, aseach item becomes available. For example an operating parameter 106 issent when a user of the ventilation system makes a change to a setvalue. When the ventilation system is turned off, the protocol signals ashutdown 411. Upon shutting down, the protocol can automatically enter apassive mode 401 (e.g., after 5 seconds).

Returning to FIG. 3, the wired adapter 304 is configured to receive 312the data according to the communication protocol 400 of FIG. 4, andconvert the data from a serial connection format to a TCP connectionformat. The wired adapter 304 then provides 314 the data in the TCPconnection format according to the communication protocol 400 of FIG. 4to a communication system 302.

The data is received from the ventilation system 102 through the wiredadapter 304 by the communication system 302. The data may be in a nativemessage format of the ventilation system 102. The communication system302 is configured to convert the data into an internal messaging formatconfigured for use with a ventilation management system 150. Theconversion can take place according to the system and method ofconverting messages being sent between data systems using differentcommunication protocols and message structures described in U.S. patentapplication Ser. No. 13/421,776, entitled “Scalable CommunicationSystem,” and filed on Mar. 15, 2012, the disclosure of which is herebyincorporated by reference in its entirety for all purposes. Thecommunication system 302 can include, for example, an interface modulefor communicating with the wired adapter 304.

The interface module can include information on the communicationprotocol 400 (e.g., VOXP protocol) and data structure used by theventilation system 102 and is configured to both receive messages fromand transmit messages between the ventilation system 102 and theventilation management system 150. For example, the ventilationmanagement system 150 is configured to provide, through thecommunication system 302 and the wired adapter 304, patient data, orderdata, configuration data, user data, preprogrammed information, vitalsign information, rules, notifications, and clinical protocols to theventilation system 102. The patient data includes, for example,admit-discharge-transfer data, allergy data, diagnosis data, medicationhistory, procedure history, a patient's name, the patient's medicalrecord number (MRN), lab results, or the patient's visit number.Medication history may include a list of the medications and doses thathave been administered to the patient, for example sedative medications,muscle paralytic medications, neural block medications,anti-inflammatory medications. Procedure history may include a list ofsurgical or other interventional procedures that have been administered,for example cardiothoracic surgery; lung lavage; maxillofacial surgery;chest physiotherapy. The order data includes, for example medicationorder information, procedure order information for at least one ofphysical therapy or percussion therapy, sedation order informationindicating sedation vacations or modes of ventilator therapy, therapyorder information for invasive or non-invasive ventilator therapy, ortrial order information for spontaneous breathing trials. Theconfiguration data includes, for example, a patient profile, a userinterface configuration, a limit configuration, a notificationconfiguration, or a clinical protocol configuration. The notificationconfiguration can indicate whether certain limits or alerts should beenabled or disabled, and the clinical protocol configuration can be usedin a particular area of the hospital 101 (e.g., ICU) and indicate whichclinical protocol library should be enabled. A clinical protocol librarymay include several clinical protocols that may be applicable to aspecified group of patients, for example a spontaneous breathing trialclinical protocol. A clinical protocol may include a set of rulesdefining actions that the ventilation system 102 should effect inresponse to events such as a change in patient physiological data, forexample a spontaneous breathing trial clinical protocol may include arule that recommences mandatory ventilation in the event that thepatient's rapid shallow breathing index (RSBI) exceeds a set threshold.As another example the spontaneous breathing trial clinical protocol mayinclude a rule that a notification should be provided on display device114 when the patient has been controlling their own respiration withinspecified limits for a period of one hour. In certain aspects, thenotifications can be generated by the ventilation management system 150and sent to the ventilation system 102 to alert a caregiver or patientnear the ventilation system 102. The user data includes, for example, anidentification of a caregiver or a healthcare institution.

After receiving the ventilator data from the ventilation system 102, theprocessor 154 of the ventilation management system 150 is configured todetermine, based on the ventilator data, a modification to the initialconfiguration profile for the ventilation system 102. In certainaspects, the initial configuration profile is received by theventilation management system 150 from the ventilation system 102. Theprocessor 154 of the ventilation management system 150 is furtherconfigured to generate a modified configuration profile for theventilation system 102 based on the determined modification. In certainaspects, the modification to the configuration profile is alsodetermined based on the initial configuration profile of the ventilationsystem 102. For example, if the initial configuration profile indicatedan average end tidal CO2 level that was considered clinically too lowfor the patient, the configuration profile could be modified to increasethe average end tidal CO2.

In certain aspects, the modification to the configuration profile isalso determined based on comparing the physiological statistics of thepatient with historical patient data (e.g., stored in the hospital data156) to identify a modification to at least one operating parameter ofthe initial configuration profile, and modify the operating parameterbased on the identification. For example, if an apnea interval that,based on historical patient data for many patients at the hospital 101,was not likely to improve the condition of the patient, then the apneainterval of the configuration profile could be modified by theventilation management system 150. As another example, if a specifiedlevel of tidal ventilation normalized to patient weight, based onhistorical patient data for many patients at the hospital 101 with aspecified diagnosis, has been associated with a reduced length ofhospital stay, then the configuration profile could be modified toadjust pressure support to target this level of tidal ventilation.

The processor 154 of the ventilation management system 150 can befurther configured to provide the modified configuration profile to theventilation system 102 for modifying operating parameters 106 in thememory 104 of the ventilation system 102. The modified configurationprofile 108 is stored in the memory 104 of the ventilation system, andused by the processor 112 of the ventilation system 102 to modify theoperating parameters 106 in the memory 104 of the ventilation system. Incertain aspects, details regarding the modified configuration profile(e.g., the modifications made to operating parameters, an identificationof a clinician responsible for approving the modifications, etc.) areprovided for display using the display device 114 of the ventilationsystem 102.

The ventilation system 102 includes a processor 112, the communicationsmodule 110, and a memory 104 that includes operating parameters 106 anda configuration profile 108. The ventilation system 102 also includes aninput device 116, such as a keyboard, scanner, or mouse, an outputdevice 214, such as a display, and a ventilation device 118 configuredto mechanically move breathable air or a gas mixture into and out oflungs in order to assist a patient in breathing according toinstructions from the ventilation system 102. The configuration profile108 includes one or many configuration profiles for operating theventilation device 118 of the ventilation system 102. For example, theconfiguration profile 108 can include a profile for operating theventilation device 118 in an intensive care unit, neonatal intensivecare unit, or surgical room, or a profile for operating the ventilationdevice 118 for patients with a specified respiratory diagnosis, such asARDS, neuromuscular disease, pneumonia, or post-surgical recovery.

The processor 112 of the ventilation system 102 is configured to executeinstructions, such as instructions physically coded into the processor112, instructions received from software (e.g., from configurationprofile 108) in memory 104, or a combination of both. For example, theprocessor 112 of the ventilation system 102 executes instructions toconfigure the ventilation device 118. The processor 112 of the of theventilation system 102 executes instructions from the configurationprofile 108 causing the processor 112 to receive, over the LAN 119, atleast one of patient data, order data, configuration data, or user data.The configuration data can include, for example, an indication (e.g., aset limit) for limiting use of the ventilation system 102 within thehospital 101. The processor 112 of the of the ventilation system 102 isalso configured to provide a modification of operating parameters 106 ofthe ventilation device 118 based on the received patient data, orderdata, configuration data, or user data.

In certain aspects the patient data received by the ventilation system102 includes a patient identifier, such as a MRN, that is obtainedthrough various processes 510, 520, and 530 and used to contextualizedata generated by the ventilation system 102 as illustrated in FIG. 5.The contextualization of data includes identifying data generated by aventilation system 102 as being data associated with a specific patient(a “patient context”). The patient context and ventilation system 102 topatient association can be stored in the memory 103 of the ventilationsystem 102 or in the hospital data 156 in the memory 152 of theventilation management system 150.

As provided in process 510 of FIG. 5, a ventilation system 102 can beassociated with a patient manually when the ventilation system 102 firstreceives in step 511 an external admit-discharge-transfer alert (e.g.,from the ventilation management system 150 or a hospital informationsystem) for a patient. Next, in step 512, the ventilation system 102 isconnected to the patient and in step 513 a caregiver, using input device116 and display device 114, searches for the patient's name oridentifier (from among a list of patient names/identifiers) on thedisplay device 114 of the ventilation system 102. The patient'sidentifier can be found, for example, using a search by care area,patient type, alphabetically, or a list of patients associated with thecaregiver. In step 514, the user validates the patient data (e.g.,selects the patient to associate with the ventilation system 102) and instep 515 the patient is associated with the ventilation system 102. Incertain aspects, a second identifier can be required, such as a medicalrecord number, in order to validate the patient data.

As provided in process 520 of FIG. 5, a ventilation system 102 can beassociated with a patient automatically when the ventilation system 102again first receives in step 521 an external admit-discharge-transferalert (e.g., from the ventilation management system 150 or a hospitalinformation system) for a patient and the ventilation system 102 isconnected to the patient in step 522. Next, in step 523, a clinicianperforms an electronic search for the patient by, for example, scanninga barcode on the patient's wrist with the input device 116 or having theventilation system 102 identify the patient using a radio frequencyidentification (RFID). Next, in step 524, the user validates the patientdata (e.g., confirms the automatically identified patient) and in step525 the patient is associated with the ventilation system 102.

As provided in process 530 of FIG. 5, a ventilation system 102 can alsobe associated with a patient automatically when the ventilation system102 is connected to a patient in step 531 and an external system (e.g.,a network scanner connected to a server, such as the ventilationmanagement system 150 or an admit-discharge-transfer system) performs asearch for the patient (e.g., using RFID). The user in step 533validates the patient data identified by the external system and theexternal system sends the patient identification to the ventilationsystem 102 in step 534. In step 535 the patient is associated with theventilation system 102. As yet another example, a ventilator may firstbe connected to a patient, the ventilation system 102 or user thenperforms an electronic search by, for example, and RFID or scannedpatient barcode, the external system validates patient data, theexternal system sends patient data to the ventilation system 102, andthe patient is associated with the ventilation system 102.

In certain aspects, both the ventilation management system 150 andventilation system 102 are configured to cache data, such as the patientdata, order data, configuration data, user data, vital sign information(e.g., physiological statistics of a patient), rules, notifications,clinical protocols, and operating parameters. Cached (or “logged”) datacan be used to perform analytics that result in improved patient care.By caching the data even when the ventilation system 102 or theventilation management system 150 are not connected, the data will havea greater chance of being used for analytics and result in improvedpatient care. The data may be cached, for example, when the LAN 119connection is unavailable. The data may then be shared between theventilation management system 150 and ventilation system 102 when theconnection becomes available. Similarly, the data may then be sharedbetween the ventilation management system 150 and ventilation system 102at regularly scheduled intervals (e.g., every 30 minutes). The scheduledintervals are configurable by a caregiver or other user, and can bebased on, for example, the data being transmitted, when a change is madeto an operating parameter of the ventilation system 102, or when ameasured value, alarm threshold, or monitored value reach a predefinedlevel or rate of change. The home ventilation device 130 can also cachedata similar to the ventilation system 102. The data may be cached bythe home ventilation device 130, for example, when the WAN 120connection is unavailable.

For example, any data that is generated by the ventilation system 102for documentation, clinical decision support, biomedical engineering ormaintenance support can be cached in the memory 104 of the ventilationsystem 102 to be sent out to the ventilation management system 150.Similarly, any data that needs to be sent to the ventilation system 102from the ventilation management system 150 can be cached in memory 152at the ventilation management system 150 until a scheduled time to sendthe data, or a next time the ventilation system 150 and ventilation areconnected.

FIGS. 6A and 6B illustrate example flow charts for caching data on aventilation system 102 and a ventilation management system 150. In FIG.6A, data 318 for the ventilation system 102, including ventilationsystem information, alarms, scalars, settings, and monitors, whenavailable, is sent to the ventilation management system 150 via aconnector 316 for storage as hospital data 156 when a connection 602between the ventilation system 102 and the ventilation management system150 is available. Otherwise, when the connection 602 between theventilation system 102 and the ventilation management system 150 is notavailable, the data is stored in a data cache 604 on the ventilationsystem 102.

In FIG. 6B, data 652 for the ventilation management system 150,including user data, alerts, preprogrammed information, lab results,patient data, and configuration information, when available, is sent tothe ventilation system 102 via a connector 316 for storage as data 658in memory 104 when a connection 654 between the ventilation system 102and the ventilation management system 150 is available. Otherwise, whenthe connection 654 between the ventilation system 102 and theventilation management system 150 is not available, the data is storedin a data cache 656 on the ventilation management system 150.

FIG. 7 illustrates an example process 700 for managing a ventilationsystem using the example ventilation system 102 and ventilationmanagement system 150 of FIG. 2. While FIG. 7 is described withreference to FIG. 2, it should be noted that the process steps of FIG. 7may be performed by other systems.

The process 700 begins by proceeding from beginning step 701 when aventilation system 102 is initialized and establishes a communicationwith the ventilation management system 150, to step 702 when theventilation system 102 provides ventilator data including at least oneof operating parameters of the ventilation device 118 or physiologicalstatistics of a patient associated with the ventilation device 118 tothe ventilation management system 150. In step 703, the ventilationmanagement system 150 receives the ventilator data from the ventilationsystem 102 and in step 704 determines, based on the ventilator data, amodification to the initial configuration profile 108 for theventilation system 102. In step 705 a modified configuration profile isgenerated for the ventilation system 102 based on the determinedmodification of step 704, and in step 706 the ventilation managementsystem 706 provides the modified configuration profile to theventilation system 102 for modifying the operating parameters 106 of theventilation system 102. The ventilation management system 706 may alsooptionally provide at least one of patient data, order data,configuration data, or user data to the ventilation system 102 in step706. In step 707, the ventilation system 102 receives the modifiedconfiguration profile and optional patient data, order data,configuration data, user data, or rules or protocols. The process 700then ends in step 708.

FIG. 7 sets forth an example process 700 for managing a ventilationsystem using the example ventilation system 102 and ventilationmanagement system 150 of FIG. 2. An example will now be described usingthe example process 700 of FIG. 7.

The process 700 begins by proceeding from beginning step 701 when aventilation system 102 in the hospital 101 is turned on and establishesa communication with the ventilation management system 150, to step 702when the ventilation system 102 provides operating parameters of theventilation device 118, physiological statistics of a patient associatedwith the ventilation device 118, and an initial configuration profile108 of the ventilation system 102 to the ventilation management system150. In step 703, the ventilation management system 150 receives thedata from the ventilation system 102 and in step 704 determines that thepatient's tidal volume has decreased over the last five minutes by 30%,which is an indication of a degradation in the patient's clinicalstatus. The data also indicates the patient's heart rate has increased.The ventilation management system 150 further determines, based on theventilator data, that the initial configuration profile 108 for theventilation system 102 should be modified to increase the breath rateparameter. In an alternative example, in step 704 the ventilationmanagement system 150 uses data from other devices such as lab resultsdata 652 including a blood oxygen measurement and a blood carbon dioxidemeasurement which indicate that the patient is being over-ventilated.The ventilation management system 150 further determines, based on thelab results data, that the initial configuration profile 108 for theventilation system 102 should be modified to decrease the breath rateparameter. In step 705 the modified configuration profile having thechanged breath rate parameter is generated for the ventilation system102 based on the determined modification of step 704, and in step 706the ventilation management system 706 provides the modifiedconfiguration profile to the ventilation system 102 for modifying theoperating parameters 106 of the ventilation system 102. Theconfiguration profile 108 of the ventilation system 102 is modified withthe modified configuration profile to increase the patient's breathrate, and the process 700 then ends in step 708.

FIG. 8 is a block diagram illustrating an example computer system 800with which the ventilation system 102, ventilation management system150, and home ventilation device 130 of FIG. 2 can be implemented. Incertain aspects, the computer system 800 may be implemented usinghardware or a combination of software and hardware, either in adedicated server, or integrated into another entity, or distributedacross multiple entities.

Computer system 800 (e.g., ventilation system 102, ventilationmanagement system 150, and home ventilation device 130) includes a bus808 or other communication mechanism for communicating information, anda processor 802 (e.g., processor 112, 154, and 136) coupled with bus 808for processing information. By way of example, the computer system 800may be implemented with one or more processors 802. Processor 802 may bea general-purpose microprocessor, a microcontroller, a Digital SignalProcessor (DSP), an Application Specific Integrated Circuit (ASIC), aField Programmable Gate Array (FPGA), a Programmable Logic Device (PLD),a controller, a state machine, gated logic, discrete hardwarecomponents, or any other suitable entity that can perform calculationsor other manipulations of information.

Computer system 800 can include, in addition to hardware, code thatcreates an execution environment for the computer program in question,e.g., code that constitutes processor firmware, a protocol stack, adatabase management system, an operating system, or a combination of oneor more of them stored in an included memory 804 (e.g., memory 104, 152,and 132), such as a Random Access Memory (RAM), a flash memory, a ReadOnly Memory (ROM), a Programmable Read-Only Memory (PROM), an ErasablePROM (EPROM), registers, a hard disk, a removable disk, a CD-ROM, a DVD,or any other suitable storage device, coupled to bus 808 for storinginformation and instructions to be executed by processor 802. Theprocessor 802 and the memory 804 can be supplemented by, or incorporatedin, special purpose logic circuitry.

The instructions may be stored in the memory 804 and implemented in oneor more computer program products, i.e., one or more modules of computerprogram instructions encoded on a computer readable medium for executionby, or to control the operation of, the computer system 800, andaccording to any method well known to those of skill in the art,including, but not limited to, computer languages such as data-orientedlanguages (e.g., SQL, dBase), system languages (e.g., C, Objective-C,C++, Assembly), architectural languages (e.g., Java, .NET), andapplication languages (e.g., PHP, Ruby, Perl, Python). Instructions mayalso be implemented in computer languages such as array languages,aspect-oriented languages, assembly languages, authoring languages,command line interface languages, compiled languages, concurrentlanguages, curly-bracket languages, dataflow languages, data-structuredlanguages, declarative languages, esoteric languages, extensionlanguages, fourth-generation languages, functional languages,interactive mode languages, interpreted languages, iterative languages,list-based languages, little languages, logic-based languages, machinelanguages, macro languages, metaprogramming languages, multiparadigmlanguages, numerical analysis, non-English-based languages,object-oriented class-based languages, object-oriented prototype-basedlanguages, off-side rule languages, procedural languages, reflectivelanguages, rule-based languages, scripting languages, stack-basedlanguages, synchronous languages, syntax handling languages, visuallanguages, wirth languages, embeddable languages, and xml-basedlanguages. Memory 804 may also be used for storing temporary variable orother intermediate information during execution of instructions to beexecuted by processor 802.

A computer program as discussed herein does not necessarily correspondto a file in a file system. A program can be stored in a portion of afile that holds other programs or data (e.g., one or more scripts storedin a markup language document), in a single file dedicated to theprogram in question, or in multiple coordinated files (e.g., files thatstore one or more modules, subprograms, or portions of code). A computerprogram can be deployed to be executed on one computer or on multiplecomputers that are located at one site or distributed across multiplesites and interconnected by a communication network. The processes andlogic flows described in this specification can be performed by one ormore programmable processors executing one or more computer programs toperform functions by operating on input data and generating output.

Computer system 800 further includes a data storage device 806 such as amagnetic disk or optical disk, coupled to bus 808 for storinginformation and instructions. Computer system 800 may be coupled viainput/output module 810 to various devices (e.g., ventilation device118). The input/output module 810 can be any input/output module.Example input/output modules 810 include data ports such as USB ports.The input/output module 810 is configured to connect to a communicationsmodule 812. Example communications modules 812 (e.g., communicationsmodules 110, 160, and 146) include networking interface cards, such asEthernet cards and modems. In certain aspects, the input/output module810 is configured to connect to a plurality of devices, such as an inputdevice 814 (e.g., input device 116) and/or an output device 816 (e.g.,display device 114). Example input devices 814 include a keyboard and apointing device, e.g., a mouse or a trackball, by which a user canprovide input to the computer system 800. Other kinds of input devices814 can be used to provide for interaction with a user as well, such asa tactile input device, visual input device, audio input device, orbrain-computer interface device. For example, feedback provided to theuser can be any form of sensory feedback, e.g., visual feedback,auditory feedback, or tactile feedback; and input from the user can bereceived in any form, including acoustic, speech, tactile, or brain waveinput. Example output devices 816 include display devices, such as a LED(light emitting diode), CRT (cathode ray tube), or LCD (liquid crystaldisplay) screen, for displaying information to the user.

According to one aspect of the present disclosure, the ventilationsystem 102, ventilation management system 150, and home ventilationdevice 130 can be implemented using a computer system 800 in response toprocessor 802 executing one or more sequences of one or moreinstructions contained in memory 804. Such instructions may be read intomemory 804 from another machine-readable medium, such as data storagedevice 806. Execution of the sequences of instructions contained in mainmemory 804 causes processor 802 to perform the process steps describedherein. One or more processors in a multi-processing arrangement mayalso be employed to execute the sequences of instructions contained inmemory 804. In alternative aspects, hard-wired circuitry may be used inplace of or in combination with software instructions to implementvarious aspects of the present disclosure. Thus, aspects of the presentdisclosure are not limited to any specific combination of hardwarecircuitry and software.

Various aspects of the subject matter described in this specificationcan be implemented in a computing system that includes a back endcomponent, e.g., as a data server, or that includes a middlewarecomponent, e.g., an application server, or that includes a front endcomponent, e.g., a client computer having a graphical user interface ora Web browser through which a user can interact with an implementationof the subject matter described in this specification, or anycombination of one or more such back end, middleware, or front endcomponents. The components of the system can be interconnected by anyform or medium of digital data communication, e.g., a communicationnetwork. The communication network (e.g., local area network 119 andwide area network 120) can include, for example, any one or more of apersonal area network (PAN), a local area network (LAN), a campus areanetwork (CAN), a metropolitan area network (MAN), a wide area network(WAN), a broadband network (BBN), the Internet, and the like. Further,the communication network can include, but is not limited to, forexample, any one or more of the following network topologies, includinga bus network, a star network, a ring network, a mesh network, astar-bus network, tree or hierarchical network, or the like. Thecommunications modules can be, for example, modems or Ethernet cards.

Computing system 800 can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.Computer system 800 can be, for example, and without limitation, adesktop computer, laptop computer, or tablet computer. Computer system800 can also be embedded in another device, for example, and withoutlimitation, a mobile telephone, a personal digital assistant (PDA), amobile audio player, a Global Positioning System (GPS) receiver, a videogame console, and/or a television set top box.

The term “machine-readable storage medium” or “computer readable medium”as used herein refers to any medium or media that participates inproviding instructions or data to processor 802 for execution. Such amedium may take many forms, including, but not limited to, non-volatilemedia, volatile media, and transmission media. Non-volatile mediainclude, for example, optical disks, magnetic disks, or flash memory,such as data storage device 806. Volatile media include dynamic memory,such as memory 804. Transmission media include coaxial cables, copperwire, and fiber optics, including the wires that comprise bus 808.Common forms of machine-readable media include, for example, floppydisk, a flexible disk, hard disk, magnetic tape, any other magneticmedium, a CD-ROM, DVD, any other optical medium, punch cards, papertape, any other physical medium with patterns of holes, a RAM, a PROM,an EPROM, a FLASH EPROM, any other memory chip or cartridge, or anyother medium from which a computer can read. The machine-readablestorage medium can be a machine-readable storage device, amachine-readable storage substrate, a memory device, a composition ofmatter effecting a machine-readable propagated signal, or a combinationof one or more of them.

As used herein, the phrase “at least one of” preceding a series ofitems, with the terms “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list (i.e.,each item). The phrase “at least one of” does not require selection ofat least one item; rather, the phrase allows a meaning that includes atleast one of any one of the items, and/or at least one of anycombination of the items, and/or at least one of each of the items. Byway of example, the phrases “at least one of A, B, and C” or “at leastone of A, B, or C” each refer to only A, only B, or only C; anycombination of A, B, and C; and/or at least one of each of A, B, and C.

Furthermore, to the extent that the term “include,” “have,” or the likeis used in the description or the claims, such term is intended to beinclusive in a manner similar to the term “comprise” as “comprise” isinterpreted when employed as a transitional word in a claim.

A reference to an element in the singular is not intended to mean “oneand only one” unless specifically stated, but rather “one or more.” Allstructural and functional equivalents to the elements of the variousconfigurations described throughout this disclosure that are known orlater come to be known to those of ordinary skill in the art areexpressly incorporated herein by reference and intended to beencompassed by the subject technology. Moreover, nothing disclosedherein is intended to be dedicated to the public regardless of whethersuch disclosure is explicitly recited in the above description.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of what may be claimed, but ratheras descriptions of particular implementations of the subject matter.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the aspects described above should not be understood asrequiring such separation in all aspects, and it should be understoodthat the described program components and systems can generally beintegrated together in a single software product or packaged intomultiple software products.

The subject matter of this specification has been described in terms ofparticular aspects, but other aspects can be implemented and are withinthe scope of the following claims. For example, the actions recited inthe claims can be performed in a different order and still achievedesirable results. As one example, the processes depicted in theaccompanying figures do not necessarily require the particular ordershown, or sequential order, to achieve desirable results. In certainimplementations, multitasking and parallel processing may beadvantageous. Other variations are within the scope of the followingclaims.

These and other implementations are within the scope of the followingclaims.

What is claimed is:
 1. A ventilation system comprising: one or moreprocessors configured to: operate the ventilator system in one of aplurality of modes for communicating ventilation information with aventilation management system; receive, from a ventilation managementsystem over a network, system data comprising at least one ofventilation configuration data, patient data, user data, or rules orclinical protocols associated with operation of the ventilation system;modify one or more operating parameters of a ventilation device based onthe received system data; receive ventilator data associated with theventilation device and a patient associated with the ventilation device,the ventilator data comprising physiological information, settings,parameters, notifications, patient information, ventilation waveforms,loops or trended data, or ventilation monitoring information; determinean alarm associated with the ventilation device or the patient based onthe ventilator data and the system data; and responsive to determiningthe alarm, transmit the alarm to the ventilation management systembefore transmitting the ventilator data to the ventilation managementsystem.
 2. The ventilation system of claim 1, wherein the one or moreprocessors are further configured to: receive a request for theventilation information from the ventilation management system; andprovide the ventilation information to the ventilation management systemresponsive to the request, wherein the ventilation information comprisesa notification, scalar, operating parameter, or physiological statisticof a ventilated patient.
 3. The ventilation system of claim 1, whereinthe one or more processors are further configured to: periodicallyprovide ventilation information to the ventilation management system,wherein the ventilation information comprises a notification, scalar,operating parameter, or physiological statistic of a ventilated patient.4. The ventilation system of claim 3, wherein the one or more processorsare further configured to: switch to periodically providing theventilation information to the ventilation management system fromwaiting for a request from the ventilation management system beforeproviding the ventilation information to the ventilation managementsystem.
 5. The ventilation system of claim 4, wherein the one or moreprocessors are further configured to: automatically switch toperiodically providing the ventilation information to the ventilationmanagement system responsive to a shutdown of the ventilation system. 6.The ventilation system of claim 1, wherein the one or more processorsare further configured to: receive, via the network, an initialconfiguration profile of a ventilation device, the initial configurationprofile including capabilities of the ventilation device, operatingparameters of the ventilation device, or physiological data of a patientassociated with the ventilation device; generate a modifiedconfiguration profile, including modified modifications made tooperating parameters, for the ventilation device based on the initialconfiguration profile and the received system data or historical patientdata for the patient; and provide the modified configuration profile tothe ventilation device to cause the one or more operating parameters tobe modified.
 7. The ventilation system of claim 6, wherein the one ormore processors are further configured to: providing for display at aclient device, based on a determination that the client device isauthorized for access to the ventilator system, a user interfaceincluding a display of configuration information for the ventilationdevice, the displayed configuration information including a current modeof operation of the ventilation device and one or more ventilationsettings affecting a current ventilation of the patient by theventilation device.
 8. The ventilation system of claim 1, wherein theventilator data is queued for transmission to the ventilation managementsystem, wherein the one or more processors are further configured to:transmit all of the ventilator data at once to the ventilationmanagement system after the alarm is transmitted.
 9. The ventilationsystem of claim 1, wherein the ventilator data is queued fortransmission to the ventilation management system, wherein the one ormore processors are further configured to: transmit a subset of theventilator data to the ventilation management system at periodicintervals after the alarm is transmitted.
 10. The ventilation system ofclaim 1, wherein the ventilation management system comprises a clientdevice.
 11. A method for communicating ventilation data, comprising:operating a ventilator system in one of a plurality of modes forcommunicating ventilation information with a ventilation managementsystem; receiving, from a ventilation management system over a network,system data comprising at least one of ventilation configuration data,patient data, user data, or rules or clinical protocols associated withoperation of the ventilation system; modifying one or more operatingparameters of a ventilation device based on the received system data;receiving ventilator data associated with the ventilation device and apatient associated with the ventilation device, the ventilator datacomprising physiological information, settings, parameters,notifications, patient information, ventilation waveforms, loops ortrended data, or ventilation monitoring information; determining analarm associated with the ventilation device or the patient based on theventilator data and the system data; and responsive to determining thealarm, transmitting the alarm to the ventilation management systembefore transmitting the ventilator data to the ventilation managementsystem.
 12. The method of claim 11, further comprising: receiving arequest for the ventilation information from the ventilation managementsystem; and providing the ventilation information to the ventilationmanagement system responsive to the request, wherein the ventilationinformation comprises a notification, scalar, operating parameter, orphysiological statistic of a ventilated patient.
 13. The method of claim11, further comprising: periodically providing ventilation informationto the ventilation management system, wherein the ventilationinformation comprises a notification, scalar, operating parameter, orphysiological statistic of a ventilated patient.
 14. The method of claim13, further comprising: switch to periodically providing the ventilationinformation to the ventilation management system from waiting for arequest from the ventilation management system before providing theventilation information to the ventilation management system.
 15. Themethod of claim 14, further comprising: automatically switch toperiodically providing the ventilation information to the ventilationmanagement system responsive to a shutdown of the ventilation system.16. The method of claim 11, further comprising: receive, via thenetwork, an initial configuration profile of a ventilation device, theinitial configuration profile including capabilities of the ventilationdevice, operating parameters of the ventilation device, or physiologicaldata of a patient associated with the ventilation device; generate amodified configuration profile, including modified modifications made tooperating parameters, for the ventilation device based on the initialconfiguration profile and the received system data or historical patientdata for the patient; and provide the modified configuration profile tothe ventilation device to cause the one or more operating parameters tobe modified.
 17. The method of claim 16, further comprising: providingfor display at a client device, based on a determination that the clientdevice is authorized for access to the ventilator system, a userinterface including a display of configuration information for theventilation device, the displayed configuration information including acurrent mode of operation of the ventilation device and one or moreventilation settings affecting a current ventilation of the patient bythe ventilation device.
 18. The method of claim 14, wherein theventilator data is queued for transmission to the ventilation managementsystem, the method further comprising: transmit all of the ventilatordata at once to the ventilation management system after the alarm istransmitted.
 19. The method of claim 14, wherein the ventilator data isqueued for transmission to the ventilation management system, the methodfurther comprising: transmit a subset of the ventilator data to theventilation management system at periodic intervals after the alarm istransmitted.
 20. A non-transitory machine readable medium comprisinginstructions stored thereon that, when executed by a machine, cause themachine to perform a method according to claim 11.